This change introduces the Hash Field Expiration feature as part of the features provided by the spring-data-redis project.

As part of the change the following commands would be made available:

• HEXPIRE - expire a set of hash fields after a specified time, measured in seconds
• HPEXPIRE - expire a set of hash fields after a specified time, measured in milliseconds
• HEXPIREAT - expire a set of hash fields at a specified UNIX time, measured in seconds since Unix epoch
• HPEXPIREAT - expire a set of hash fields at a specified UNIX time, measured in milliseconds since Unix epoch
• HEXPIRETIME (omitted on the grounds it is missing for keys too)
• HPERSIST - persist a field that was previously marked for expiration
• HTTL - return the time-to-live of a given hash field in seconds
• HPTTL - return the time-to-live of a given hash field in milliseconds

The new commands are available as part of the following interfaces:
(based on similar PR #283)

• RedisHashCommands
• HashOperations / BoundHashOperations
• ReactiveHashOperations
• StringRedisConnection

This feature is available starting from Redis CE version 7.4.x and later

For more information on HFE you can also check out ...
... the blog article on the topic.
... examples of how one can take advantage of the feature in their application

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).